feat: add step-up auth scenario for server auth testing #106
+346
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- New StepUpAuthScenario tests 403 insufficient_scope handling - Verifies server returns proper WWW-Authenticate with scope/resource_metadata - Verifies client re-authenticates with elevated scope - Tests successful request after scope escalation
commit: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Adds a step-up authentication scenario to test servers' handling of scope escalation via 403 insufficient_scope.
What's New
New Scenario:
server-auth/step-up-authTests the complete step-up authentication flow:
Conformance Checks
step-up-403-response- Server returns 403 with insufficient_scope errorstep-up-scope-in-header- WWW-Authenticate includes required scopestep-up-resource-metadata- WWW-Authenticate includes resource_metadatastep-up-re-auth- Client re-authenticated for elevated scopestep-up-success-after-escalation- Request succeeds after scope escalationSpec References
Related PRs